Enabling Localized Content

How to create a localized copy of the current site content for each of the enabled languages using the LanguagesMultiple languages (cultures) can be enabled on DNN. This can be enabled for the DNN framework (e.g. the field names on the Edit pages) and for the site content by creating content in each language using content localization. module. This creates a translator role ( titled Translator and then appended with the country code. E.g. Translator (EN-AU) ) for each enabled language. This also enables the Localization tab under PageA page on a DNN site. Settings for all site pages. See "Localization Settings for New Pages" DNN Platform users (including anonymous users) must be granted Edit ModuleDNN uses a modular design system to display content on a page. One or more modules are added to each site page to create and manage the site content. There are many different types of modules, each managing a different type of site content or site administrative tasks. permissions. Evoq Content users (including anonymous users) must be granted Edit Content permissions.

Prerequisite. Localized content must be enabled by a SuperUserThese users have full access to manage the settings and content of all sites with this DNN installation, including the Host site. SuperUser accounts are created using the Host > SuperUser Accounts module.. Localized content cannot be disabled once it has been enabled. See "Allowing/Disallowing Content Localization"

1. Navigate to AdminRegistered users who are members of the Administrators role. These users have full access to manage the site including adding, deleting and editing all pages and modules. Administrators also have access to the Admin pages located on the main menu. > Advanced Settings > LanguagesMultiple languages (cultures) can be enabled on DNN. This can be enabled for the DNN framework (e.g. the field names on the Edit pages) and for the site content by creating content in each language using content localization. - OR - Go to a LanguagesMultiple languages (cultures) can be enabled on DNN. This can be enabled for the DNN framework (e.g. the field names on the Edit pages) and for the site content by creating content in each language using content localization. module.
2. Select the LanguagesMultiple languages (cultures) can be enabled on DNN. This can be enabled for the DNN framework (e.g. the field names on the Edit pages) and for the site content by creating content in each language using content localization. tab.
3. Click the Enable Localized Content button.

4. The Enable Localized Content message box is now displayed listing the Current SiteRefers to a single and unique site created using DNN. Multiple unique sites can be created and managed within each installed DNN application. Default language and informing that this language cannot be changed once localized content is enabled. To change the default site culture, select Cancel now and then change the default language.
5. At Make all pages Translatable, select from these options:
   • Mark  the check box if all pages that are in the default language will be made translatable. This creates a copy of all translatable pages for each of the enabled languages.
   • Unmark  the check box to translate some of the pages that are in the default language into other languages. This allows some or most of the site to be maintained in the default language and only manage selected pages, such as the contact page or pages that don't frequently change content, into other languages. This is the default setting.

6. Click the Enable Localized Content button. This displays progress bars that show the languages and pages being created for each of the enabled languages and creates a copy of each of these pages (including the modules and content on these pages) for each language. It also creates a translator role for each language. Once this step is complete, a new tab called "Content Localization" is available on the LanguagesMultiple languages (cultures) can be enabled on DNN. This can be enabled for the DNN framework (e.g. the field names on the Edit pages) and for the site content by creating content in each language using content localization. module and a new section titled Content Localization is displayed in the culture grid with the following new fields:
   • No of Pages: This displays the number of pages and the percentage of pages that have been localized. Note: In this example, the number of pages is shown is zero ( 0 ) for the default language of English (United States) as no pages have been localized as yet. For each of the other enabled languages, the No of Pages button is displayed as a link that can be clicked to create localized pages for that language. Each enabled language displays this button, allowing different pages to be localized for each language as required.
     If all pages were chosen from translation then the number of pages that were localized (e.g. 12) would be the same for the default language of English (United States) and all other enabled languages and percentage of localized pages would be 100%.
   • Translated Pages: This displays the number of page and the percentage of pages that have been translated.
   • Active: Localized content is activated / not activated.
   • Publish: The Publish Pages icon enables editors to publish pages that are marked as translated for this language.

To view the newly created localized copies for this language, click on the country flag for this language (typically located in the top right corner of the site above the menu). This displays the localized copies of these pages in the menu. Note: PageA page on a DNN site. names are appended with the country code. E.g. For Australia it is (EN-AU). Modify these names by editing the PageA page on a DNN site. Name. See "Setting Page Details"

A translator role named Translator (en-AU) is now displayed in the Security RolesRoles control which users can view and manage site pages and content. Roles can be created using the Admin > Security Roles page or by creating Social Groups. module for each language that is enabled. Before translation can begin, the users who are the translators for each language should be added to the newly created translator roles. See "Adding a User to a Role"

Tip: Assign additional roles and users as translators for a language. See "Setting Translator Roles"

Next Step: The site is now ready for translation. See "Translating a Page" or See "Translating a Module".

Open topic with navigation